Using FullTextSearch’s SearchService to retrieve pages:

public PagedSearchResult SearchPages(IPublishedContent? rootNode, string searchTerm, int pageNumber, int pageSize)
{
    if (string.IsNullOrWhiteSpace(searchTerm) || rootNode == null)
    {
        return new PagedSearchResult();
    }

    string culture = Thread.CurrentThread.CurrentUICulture.Name.ToLowerInvariant();

    var search = new Our.Umbraco.FullTextSearch.Models.Search(searchTerm)
        .EnableHighlighting()
        .AddTitleProperty("nodeName")
        .AddSummaryProperty("bodyText")
        .SetSummaryLength(300)
        .SetPageLength(pageSize)
        .SetCulture(culture)
        .AddRootNodeId(rootNode.Id);

    var ftsResult = _ftsSearchService.Search(search, pageNumber);

    var paged = new PagedSearchResult
    {
        TotalItemCount = ftsResult.TotalResults,
        CurrentPage = (int)ftsResult.CurrentPage,
        PageSize = pageSize,
        TotalPages = (int)ftsResult.TotalPages,
        Results = ftsResult.Results.Select(x => new SearchResultItem
        {
            Content = x.Content,
            Title = x.Title,
            Summary = x.Summary?.ToHtmlString() ?? string.Empty,
            Score = x.Score
        }).ToList()
    };

    return paged;
}

The search worked perfectly before enabling “Restrict Public Access” on blog pages. After protecting the pages, summaries are incorrect, displaying only the HTML content of the login page instead of the expected blog content. The FullTextSearch package likely fetches page content as an unauthenticated user, meaning it only sees the login page instead of the real content behind authentication. Since the indexing process isn’t authenticated, the indexer stores the login page’s text inside bodyText, causing incorrect search results. Disabling protection → Works perfectly, so the issue is definitely related to authentication. Is there any way to allow FullTextSearch to index protected content properly while keeping pages restricted for non-members? Can I authenticate the fetcher somehow? Has anyone encountered this issue and found a solution? This is critical because my site is about to go live, and I need to keep the authentication in place while ensuring that search results display correct summaries instead of login page content. I appreciate any insights or suggestions! Thank you in advance for your help. 😊

Also, if you the search function is available to unauthenticated users, beware that "authenticating" the indexing process, will make indexed authenticated content used for summaries available for unauthenticated users too.

And I also only have one member group, which means that every user who logs into the intranet is created as a member with access to the “IntranetMembers” group and all members are simply in there, and there won't be any other groups.

The bodyText is always empty then...